home *** CD-ROM | disk | FTP | other *** search
- Path: rkadw1.ple.af.mil!usenet
- From: thrasher@rkami2.ple.af.mil (Durwood Thrasher)
- Newsgroups: comp.sys.amiga.applications
- Subject: Re: UUencode
- Date: 5 Feb 1996 17:54:40 GMT
- Organization: Phillips Laboratory Edwards
- Message-ID: <4f5g90$bc@rkadw1.ple.af.mil>
- References: <4edic0$auv@kdcol.kdcol.com> <19960128.4183E0.B91B@ak102.du.pipex.com> <p3KrAjf.anderson4@delphi.com>
- NNTP-Posting-Host: rkami2.ple.af.mil
- Mime-Version: 1.0
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- X-NewsSoftware: GRn 2.1 Feb 19, 1994
-
-
- In article <p3KrAjf.anderson4@delphi.com> Stanley Anderson <anderson4@delphi.com> writes:
- > Mathew Hendry <m.hendry@dial.pipex.com> writes:
- >
- > >uuencode myfile >newfilename
- >
- > You can include the volume designation (ram:, dh0:, etc.) as part of the
- > filename...thus allowing, for instance to uuencode a file from hard drive,
- > into ram.
- >
- > Stan Anderson
- --
- I think it's a little more complicated than that. The format I have to use to
- get uuencode to work is:
-
- uuencode <myfile >newfilename myfile
-
- (Note that myfile appears twice.)
-
- thrasher@rkadw1.ple.af.mil
-
- Durwood Thrasher
- Phillips Laboratory
- OLAC PL/RKAM
- Edwards AFB, CA 93524-7015
- (805)275-5221 FAX: 275-5719
-